feat(nuxt): Add deployment-platform flow with links to docs #747
Conversation
|
src/nuxt/nuxt-wizard.ts
Outdated
| if (canImportSentryServerConfigFile) { | ||
| msg += `\n\nAfter building your Nuxt app, you need to ${chalk.cyan( | ||
| '--import', | ||
| )} the Sentry server config file.\n\nFor more info see: ${chalk.cyan( | ||
| 'https://docs.sentry.io/platforms/javascript/guides/nuxt/install/cli-import/#initializing-sentry-with---import', | ||
| )}`; | ||
| } |
There was a problem hiding this comment.
l: given that this is a pretty crucial step, I was thinking that we could make this a step that users have to confirm instead of showing this in the outro message.
So basically, print this message and make them confirm the step with an "Ok, I got it" or so. There's similar precedence for something like this in our source map wizard.
I'll leave this up to you though, so feel free to go with whatever you prefer.
There was a problem hiding this comment.
Thanks, good idea! What if we (also?) opened up the docs for them with that link since it's pretty crucial that they read the info on there?
There was a problem hiding this comment.
I like it! I think it's most important to have this one extra step so that people actually read what the wizard tells them, before the outro message is printed. Asking about opening docs achieves this well. Thanks!
Co-authored-by: Lukas Stracke <[email protected]>
andreiborza
force-pushed
the
ab/deployment-platform
branch
from
f80815a to
31fa5d9
Compare
We now ask where users plan to deploy their app:
For Vercel and Netlify we configure top level import of the Sentry server config file and link to docs:
For other/none we instruct people at the end to
--importtheir Sentry server config file and link to docs:This also improves the handling when a user's nuxt config can not be read. Instead of exiting the wizard, we continue and instruct people how to manually add it (already existed, but we bailed immediately after instructing).
Closes: #739